Methods for reading data in a utility meter

ABSTRACT

In one aspect, the present disclosure relates to a method to read energy-related data in a power meter. In one exemplary embodiment, the method includes the step of sending a request message to an on-premise processor, directing the on-premise processor to read energy-related data from a power meter, using an 802.11 X-based wireless protocol. The method further includes the step of retrieving energy-related data stored in a memory of the power meter by the on-premise processor, using the 802.11 X-based wireless protocol, and the step of receiving a response message sent at a host processor, communicated from the on-premise processor, using the 802.11 X wireless protocol. The method further includes the step of recording the energy related data in a data structure in memory of the host processor, along with a date and time information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation and claims priority to and benefit ofco-pending U.S. patent application Ser. No. 12/259,975, filed Oct. 28,2008, entitled “Systems and Methods for Remote Power Management Using802.11 Wireless Protocols,” the status of which is allowed, which claimspriority to and is a continuation of U.S. application Ser. No.12/028,730, entitled “Systems and Methods for Remote Power ManagementUsing 802.11 Wireless Protocols,” filed Feb. 8, 2008, now U.S. Pat. No.7,451,019, which is a continuation of U.S. application Ser. No.11/370,705, entitled “Systems and Methods for Remote Power ManagementUsing 802.11 Wireless Protocols,” filed Mar. 8, 2006, now U.S. Pat. No.7,349,766, which is a divisional of U.S. patent application Ser. No.10/658,493, entitled “Systems and Methods for Remote Power ManagementUsing 802.11 Wireless Protocols,” filed Sep. 8, 2003, now abandoned,each of which are hereby incorporated by reference as if set forthherein in their entirety. Claims 1-70 were originally filed in the '493application on Sep. 8, 2003. Claims 43-51 in the present continuationapplication correspond to the subject matter in claims 43-51 of the '493application as originally filed.

FIELD OF INVENTION

This invention is directed to systems and methods for remote powermanagement using the IEEE 802.11 suite of wireless protocols to effectvarious power management functions including: power load control, powermeter activation and deactivation, and utility meter data gathering forresidential and commercial applications.

BACKGROUND AND SUMMARY OF THE INVENTION

The growth in energy consumption has outstripped the power generatingcapabilities in various areas. It is not uncommon in various regions forpower utilities to mandate temporary reductions in power usage becauseof limited power generating capabilities. This is most prevalent in thesummertime in conjunction with hot weather, when air conditioning usagepeaks. Such air conditioning loads often represents the single largestpower consumption loads for many residential and business locations.

In other instances, the power supply in the aggregate for a region isable to meet the power demand for the region, but limitations in thepower distribution and transmission infrastructure result ininstability, or unequal availability of power throughout the region. Theblackout in the northeastern United States on Aug. 14, 2003 illustratesthat impact of problems in power transmission and distribution can alsolead to power outages and load imbalances.

If power consumption exceeds the available supply, regardless ofinsufficient power generation or inadequate distribution andtransmission facilities, the power grid has automatic safeguards tolimit the demand and prevent permanent damage to the power grid. Theseprocedures may result in power blackouts and are undesirable as theyindiscriminately remove power to all users located in a service areawithout warning. Another approach is to temporarily eliminate power on aplanned basis to a selected service area. While still undesirable, thisapproach has the benefit of being planned and the impact (e-g., areaeffected) is known in advance. However, the economic costs of suchblackouts is significant, and has been estimated by the government tocost the U.S. economy between $119-$188 billion dollars annually.

More preferable to rolling blackouts are approaches where power ismaintained, but consumption is reduced so as to avoid a subsequentblackout. Typically, large power consumers (e.g., commercial andindustrial customers) voluntarily enter into a demand load reductionprogram offered by the power utility. These arrangements are typicallyregulated by an appropriate state regulatory agency (e.g., PublicUtility Commission) and in this arrangement customers agree to reduce oreliminate their load consumption upon request of the utility in exchangefor a lower energy prices (power rates). Customers are typicallyrequested to reduce their power consumption for a fixed number of hours(e.g., four hours) upon request, for a fixed number of times a year(e.g., six per year). If at the time of the request the customer doesnot reduce their power, then a penalty is levied on the customer. Thisrequires the power utility to individually contact large energyconsumers and request load reduction, which typically is accomplished byuser deactivating a power load. Frequently, these users ‘turn off’ ordeactivate air conditioning systems or other industrial processes for alimited time period when usage is predicted to peak (e.g., typicallyafternoon). Often, peak usage is predictable and involves comparing pastusage and anticipated temperatures. Thus, the need for limitingconsumption can be often predicted hours in advance.

Typically, the power utility maintains a list of customers that consumelarge amounts of power, with names and telephone numbers for the purposeof requesting voluntary reduction in power usage. If a power reductionis required, utility personnel will telephone the customers and requestpower reduction. Under the incentive/disincentive programcharacteristics, customers typically comply as the alternative typicallyresults in penalties and the ultimate result in a blackout.

The process of manually contacting and deactivating power loads is laborintensive and slow. Further, once a power utility contacts a customerfor load reduction, the power utility has no immediate feedback as towhether the customer did reduce their power consumption and theassociated impact. Typically, determination of a power load reduction isdetermined at the end of the billing cycle, and it is not clear whetherthe load was reduced for the entire time period or not. In addition, thepower utility is not readily able to determine the real time powerdemand reduction by such power load demand activities, except at a veryaggregate level. Consequently, the power utility may request far more(or less) power consumers to reduce their load than is required.Further, the power company is not able to tailor the time period forwhat is required. For example, the power utility may request loaddeactivation for a 4 hour window, but if after 3 hours it is determinedthat no further load reductions are required, the utility may notcontact the various power consumers indicating that load reduction isnot longer required. Contacting each of the power consumers may take solong so as to render the process moot.

Clearly, an automated approach for managing loads would be preferable.Further, the management of power loads may allow distinguishing betweenvoluntary reduction and involuntary reduction. For example, if a powerprovider requires reducing power consumption, it may be preferable toobtain power reduction by voluntary load reduction, rather, than toinstitute involuntary power reduction. Typically, only if the voluntaryreductions are insufficient are involuntary power reductions instituted.Thus, in managing loads, a user may require to know the distinctionwhether an indication for power reduction is a voluntary request or aprecursor to a demand for power reduction. Further, automated approachesmay allow flexibility in defining load reduction programs. Users mayselectively volunteer to reduce their power consumption if economicincentives are provided to them even, if they have not enlisted into atraditional power load reduction scheme. Thus, users not enlisted in apower load reduction scheme could still be offered an economic incentivevia variable rate schedules for power consumption. A normal, or ‘offpeak’ usage rate indicates the rate normally used to calculate a billfor power usage while a ‘peak rate’ indicates a higher rate for peakdemand. However, communication of a dynamic schedule of peak/off peakrates can be scheduled on a real time basis to hundreds or thousands ofusers that would not be practical on a manual basis. Therefore, anautomated approach for communicating rate schedules would be preferable.

Existing technology has not proven practical in many instances inaddressing these problems, partly from a cost perspective. However, thewide scale development of a relatively recent developed wireless LANstandard known as IEEE 802.11 allows the low cost application ofwireless technology to address many of the above problems, as well asproviding additional benefits.

A major impediment to the application of wireless data communicationtechnology is that in many circumstances, radio transmission is limitedby regulation by the FCC. The FCC defines frequency bands, (‘spectrum’)which are subject to various regulations regarding its use and technicaloperation. For example, transmission of radio frequencies in mostspectrum is regulated and only available for use by licensed entities.Thus, a power utility desiring to utilize wireless technology toremotely manage power loads would have to, in many cases, obtain a FCClicense and comply with the associated regulations. In many instances,the regulatory compliance is complicated, and obtaining a license forusing the spectrum can be very difficult and costly. Typically, alicense requires a significant revenue producing application to justifyits use.

The FCC has allocated a portion of the spectrum for unlicensed use, asdefined in a portion of the regulations known as ‘Part 15’ of Title 47of the Code of Federal Regulations. So-called ‘Part 15’ devices includegarage door openers, cordless telephones, walkie-talkies, baby monitors,etc. These devices operate on defined channels in frequency bands andare subject to interference from other devices. To minimizeinterference, the FCC limits the maximum power that may be used duringtransmission.

A technology developed initially for the military radio communications,called ‘spread spectrum’ has been adapted for cellular applications andis now available for use in other applications at very economical costs.This technology has the benefit of minimizing interference from otherdevices using the same bandwidth. This technology is mandated by the FCCfor equipment transmitting in a portion of the unlicensed spectrum,namely frequencies of 2.4 to 2.4835 GHz. The devices in this rangetypically are allowed to transmit at a maximum of 1 watt, though mosttransmit at a lower power. This technology allows a variety of users toshare the spectrum and minimize interference with each other.Heretofore, the historical approach to minimizing such interference wasto license the frequency to a specific entity, which in turn coordinatesindividual users (typically in the role of a service provider inrelation to its subscribers).

The IEEE (Institute of Electrical and Electronics Engineers) sponsorsvarious standards settings bodies, and the group known by the numericaldesignator “802” is responsible for various Local Area Network (LAN)standards. A group formed to define various wireless technical standardsfor LAN standards, is known as 802.11. This group has defined variousapproaches for using spread spectrum techniques in the unlicensed2.4-2.4835 GHz spectrum for LANs and has spawned an entire industry ofmanufacturers building equipment allowing wireless data communicationfrom various devices including laptops, PDAs, and other devices.

The 802.11 group has divided into various task groups focusing onvarious technologies and has evolved over time. The following lists someof the task groups and their focus:

802.11—Wireless LAN Physical and MAC layer specification (2.4 GHz.),

802.11a —Wireless LAN Physical and MAC layer specification (SGhz),

802.11b—Higher speed (5.5 and 11 Mbps),

802.11c—Bridge Operations,

802.11d—Operation in additional regulatory domains,

802.11e—Quality of Service parameters,

802.11f—Multi-vendor access point interoperability Access DistributionSystems,

802.11g—Higher rate (20 Mbps) extensions in the 2.4 GHz band,

802.11h—Enhancements for Dynamic Channel Selection,

802.11i—Security and Authentication.

Thus, the 802.11 suite of protocols encompasses a variety of past andpresent protocols designed to inter-work together.

The 802.11 protocols are based typically on using TCPIIP protocols,which are well known in the art and adapted from wireline LAN usage.This facilitates. interworking of existing infrastructure (e.g.,hardware and software) for use with the wireless LAN equipment.

The wireless LAN task groups have defined various wireless architecturesincluding end-points (also called stations) that originate and terminateinformation, and access points that provide access to a distributioninfrastructure for extended communication. The 802.11 standard definesvarious capabilities and services associated with an end devicepertinent to wireless operation. For example, 802.11 defines proceduresto authenticate an end-point to an access point, associate/disassociatedan end-point to an access point, ensure privacy and security, andtransfer data between an 802.11 LAN and non-802.11 LAN.

The development of these standards along with industry cooperation toensure interoperability has lead to equipment which when certified istermed “Wi-Fi” and can provide for wireless data communicationheretofore not possible. The large-scale development of specializedsemiconductors has lead to economies of scale allowing low costequipment that heretofore has not been possible for wireless products.Thus, the use of 802.11-based equipment provides a whole new opportunityfor communication capabilities for devices heretofore not possible. Thisallows greater automation and control for applications previously notconsidered.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates the prior art of an application of 802.11b wirelesscommunication involving a personal computer.

FIG. 2 illustrates one embodiment of the basic architecture forcommunication involving an end device, a power meter incorporating anintegrated on-premise processor, and an energy management host accordingto the principles of the present invention.

FIG. 3 a illustrates one embodiment of a power meter with an integratedprocessor for energy management.

FIG. 3 b illustrates one embodiment of an air conditioning thermostatwith an integrated processor for energy management.

FIGS. 4 a-4 d illustrate various protocol stacks associated with variousembodiments of the basic architecture.

FIG. 5 illustrates various embodiments of distribution networks forfacilitating communication between the on-premise processor and amanagement host according to the principles of the present invention.

FIG. 6 illustrates one embodiment of a distribution network comprising amesh network of on-premise processors embodied in power meters accordingto the principles of the present invention.

FIG. 7 illustrates various embodiments of end devices communicating witha on-premise processor according to the principles of the presentinvention.

FIG. 8 illustrates one embodiment of energy management according to theprinciples of the present invention.

FIG. 9 illustrates one embodiment of an architecture of the host systemaccording to the principles of the present invention.

FIG. 10 illustrates one embodiment of a data structure for maintainingmeter data in the host according to the principles of the presentinvention.

FIG. 11 illustrates one embodiment of an energy load control applicationaccording to the principles of the present invention.

FIG. 12 illustrates another embodiment of an energy load controlapplication according to the principles of the present invention.

FIG. 13 illustrates yet another embodiment of an energy load controlapplication according to the principles of the present invention.

FIG. 14 illustrates yet another embodiment of an energy load controlapplication according to the principles of the present invention.

FIG. 15 illustrates an embodiment of an energy load control applicationinvolving an appliance according to the principles of the presentinvention.

FIG. 16 illustrates an embodiment of an energy load control applicationinvolving deactivation of a load according to the principles of thepresent invention.

DETAILED DESCRIPTION

The present invention is directed, in part, to remote energy loadmanagement, including power load control, real time load curtailmentverification, meter, activation/deactivation, and meter reading.Although the principles of the present invention are largely illustratedusing a power meter and load control device, the principles equallyapply to other embodiments of resource management. For example, in lieuof a power load and power meter, a natural gas flow controlled by avalve or gas meter could be used. Other examples include devicescontrolling resources in the form of fluids, solids, and thecorresponding devices for metering or handling such fuel resources ascoal, oil, gasoline, diesel fuel, kerosene, etc. A variety of measuredresources controlled by a metering device may be adapted to theprinciples of the present invention. Thus, illustrating the principlesby using a power meter should not be construed to limit application ofprinciples of present invention solely to such embodiments.

One of the several main functions associated with energy managementinclude power load control, or simply ‘load control.’ This refers to anexternal entity, which in some cases is associated with the powerprovider (e.g., power utility company) influencing the control of apower load. The ‘control’ of the load can take various forms, includingdeactivating a load, requesting deactivation of a load, requestingdeferment of activation of a load, requesting the activation of on sitegenerating capacity (e.g. distributed generation) or even advising anintelligent load controller of the relative rates associated with powerconsumption. For example, one embodiment of load control is controllingthe activation of an air conditioning system. For many energy relatedapplications, air conditioning systems represent the single largestpower load at a location. Typically, the control of whether such systemsare ‘on’ or ‘off’ occurs using a thermostat in an autonomous manner.More sophisticated building control systems may integrate a processor tocontrol the A/C systems so that they are only activated during businesshours. Such systems may define preset temperature levels to preventindividuals from overriding the settings.

One motivation for controlling power loads occurs when the power utilitycompany is not able to fully supply the electrical power demands for allusers. This results in ‘brownouts’ or ‘rolling blackouts,’ and typicallyoccurs in the summertime during peak usage. From the power utilitycompany's perspective, it is imperative that when the demand exceeds theavailable power, that loads be controlled. Otherwise, various automaticmeasures in the power grid will automatically reduce loads to preventharm to the power grid. This results in an unplanned blackout, which isa total termination of power to selected service areas.

One solution is for the power utility company to selectively terminatepower in certain areas (‘rolling blackout’). Another solution, which isoften preferable, is to lower the load by terminating selected energyintensive loads (e.g., A/C systems). One method of accomplishing this isfor the power utility company to telephone selected customers andverbally request deactivation of A/C units at a specified time for aspecified duration. Alternatively, the power utility company can requestthe customer to alter their power consumption in other ways. Forexample, the power company can request a customers to set A/Cthermostats at a higher temperature.

Another method for reducing consumption involves an economic basedincentive where usage rates may be increased during peak usage hours(e.g., typically during afternoon business hours). This relies on usersto monitor their usage carefully and adjust their power consumptionaccordingly.

However, these schemes heretofore have relied on manual intervention.While many sophisticated control systems may be deployed to controllingloads, the inability to communicate and readily exchange information hashindered more efficient power load control approaches. The incorporationof 802.11X-based wireless capabilities offers the ability to overcomethis problem in a cost effective manner, and allow full integration ofremote management capabilities for power load control.

As used herein, 802.11X (upper case ‘X’) does not specifically refer toa task group within the 802.11 committee structure, nor a specificstandard of a task group. While there is a set of capabilities known as802.11x (lower case ‘x’), which focuses on a method for transporting anauthentication protocol between the client and access-point devicesinvolving the Transport Layer Security (TLS) protocol, the term 802.11X(upper case) as used herein refers to any of the protocols andprocedures associated with the 802.11 wireless communications, including802.11a, 802.11b, 802.11g and others (including 802.11x) that may beused singularly or in conjunction with each other. Further, evenpre-cursor wireless protocols, such as “Bluetooth” are considered to bea variation of 802.11X-based protocols and thus within the scope of802.11X.

The present inventions now will be described more fully hereinafter withreference to the accompanying drawings, in which some, but not allembodiments of the invention are shown. Indeed, these inventions may beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein; rather, these embodiments areprovided so that this disclosure will satisfy applicable legalrequirements. Like numbers refer to like elements throughout.

Turning to FIG. 1, this figure illustrates one embodiment of the priorart regarding the use of IEEE 802.11b for wireless data communicationsinvolving a personal computer. A personal computer 15 is configured with802.11b capabilities, either by incorporating an 802.11b accessory boardor having the 802.11b capability integrated into the system. Thepersonal computer communicates wirelessly using radio waves 14 with anaccess point 13. The range of communication is based in part on thepower of the radio signal and the data rate, and is typically 100-200feet, which is an adequate range for many residential applications. Theaccess point 13 is typically connected to a communications network,using devices such as a cable modem 12 (or DSL modem). The cable modemprovides high-speed access via a cable facility 11 to the Internet 10.Though illustrated as a single network, the Internet 10 is actually acollection of networks cooperating to form a single logical Internet 10as is well known to those skilled in the art.

A host processor 6 is illustrated as connected via a communicationsfacility 17 (such as a T1 communications line) to the Internet 10. Thecommunication facility 17 can be any type of the high speed digitalfacilities commonly used. This architecture allows the user toseamlessly communicate using a TCP/IP connection 16 with the host 6.

This architecture can be adapted for remote energy management asillustrated in FIG. 2. In FIG. 2, there are three main components in theembodiment illustrated: these are the end device, illustrated as anintelligent air-conditioning (A/C) thermostat 2; an on-premise processorincorporating an on-premise processor and additional functionality,illustrated as an intelligent power meter 4; and an energy managementhost processor 6.

“End device” as used herein is a generic descriptor for any type ofdevice that initiates and terminates data transmitted to the on-premiseprocessor. As used herein, an “end device” is not limited to thefunctionality of an end station as defined in the 802.11. architecture,but may incorporate additional functions, including applications forcontrolling loads, processing energy-related data and so forth. Enddevices may be embodied in various forms, typically by augmenting acontroller of some sort with the capability to transmit and receiveinformation using the appropriate 802.11X-based wireless standard. Inthis illustration, an intelligent A/C thermostat is an end device, andmay comprise an A/C thermostat that has been adapted with a processorand programmed for allowing remote load management.

The second main component in the architecture embodied in FIG. 2 is theOn-Premise Processor (OPP). As used herein, an OPP may include thecapabilities of an access point as defined in the 802.11X-basedarchitecture, but the OPP typically includes additional capabilities andfunctions. An on-premise processor may be simply a relay of information,or the OPP may perform additional processing and control functions. Anon-premise processor requires the hardware and software to perform the802.11X-related functions, and typically does terminate and process theapplication layer protocol information. The OPP is typicallyprogrammable so that various value-added applications can be implementedby software resident on the OPP or downloaded by the host. The OPPillustrated herein as an ‘intelligent power meter’ 4 is just oneembodiment. Other embodiments may involve an OPP that is internallyco-located with the power or other type of meter, externally co-locatedwith the meter, or some other variation.

The third main component in the architecture is the host processor 6.This may be a computer, such as a PC, mini computer, or host server. Itincorporates the typical hardware and software associated with atransaction oriented host processor, including a database for retainingaddress and data for numerous distinct and separate power loads. Thehost processor may be an integral part in controlling the power load,either directly or directly, in addition to performing other functionsas will be discussed. The details of a host embodiment will be discussedsubsequently.

In the embodiment illustrated in FIG. 2, the end device 2 is located inthe vicinity of the OPP 4. As illustrated by the dotted line 1, thesedevices are typically in close proximity of each other, typically within100-200 feet. The term “on premise processor” reflects one embodiment ofhaving the processor 4 located at the same premises as the end devicefrom the perspective of the host. Thus, the host views the processor 4as located in the same location or premise as the load. Thecommunication between the end device and OPP is typically via wirelesscommunication 5 at a relatively low power, since typically a shortdistance is involved. The proximity of the OPP 4 and the host processor6 is variable, and frequently these can be located in differentgeographic areas, as in different cities or even states. It is notnecessarily the case that the technology used between the end device andOPP is the same technology used as between the OPP and host. Thecommunication link 7 between the OPP 4 and host 6 may be variouswireless or wireline based communication facilities, including802.11X-based wireless technologies.

The end device can also establish communications 9 with the host on apeer-to-peer basis. However, since the end device utilizes a limitedpower 802.11X-based wireless communication capability, thecommunications link between the end device and host may involve the OPPacting as a relay and/or a protocol converter. Because the radio rangeof the end device may be limited, the OPP facilitates communication witha distant host. Further, because the host may not implement any form of802.11X-based wireless communication, the OPP acts to convert thewireless protocol into a protocol format recognized by the host, whichmay even be wireline based. This allows the host processor to beisolated from the changes in the 802.11X-based technology, and viceversa.

FIG. 3 a illustrates one embodiment of the On Premise Processor 202 thatis integrated with a power host meter 200 to form an integrated system201. In FIG. 3 a, the system 201 is depicted as co-located within theglass and metal housing of a power meter. Thus, all the components ofthe system 201 are typically inaccessible to non-service personnel.Typically, the only connections into/from the system are for providingunmetered power 203 into the system or metered power 205 from thesystem.

There are two main portions of the system comprising a host power meter200 and the On Premise Processor 202, which is also referred to as an‘On Board Processor’ because the processor is typically co-located withthe same circuit board containing components associated with the meter.The OPP may be mounted on the same circuit board containing the othercomponents or may be on a separate circuit board that 25 connects insome manner to another circuit board. The meter portion 200 obtains andretains power related measurements, including usage, status, and powerquality measurements. It communicates with the OPP portion 202 via adefined interface 207. Although this may be embodied as a connector, itmay also be embodied as a logical interface only. One aspects of theinterface is that various types of data 206 are provided 30 from themeter to the OPP and the OPP may issue control commands 208 to themeter, such as providing data requested by a control command.

The OPP is controlled by a processor 210 which can be one of varioustypes of microprocessor or microcontroller chips. The processor 210typically interacts with memory 214 that includes both volatile 214 aand non-volatile memory 214 b. The processor also can communicate datato/from the host by using a wireless data transceiver 216 thatsending/receiving data using radio waves using an antenna 218. Themicroprocessor 210 provides visual status indications via various statusLEDs 212, which may facilitate diagnosing the status or condition of thesystem by service personnel. The processor 210 also interacts withvarious circuits to ensure continuous operation, namely a wakeup timer224, a timer 222, and a CPU supervisor 220. The wakeup timer 224 ensuresthat the CPU exits a sleep mode after a reset has occurred. The timer222 ensures the application executed by the CPU does not ‘lock up’ in anunknown state. If this occurs, the timer will function as a watchdogtimer and reset the CPU. The timer 222 also functions to maintain realtime so that elapsed time or current time may be noted by themicroprocessor. Finally, the CPU supervisor 220 ensures that when abrownout or reset occurs, the restoral of the CPU occurs in an orderlymanner, including that the input voltages are sufficient. Theaforementioned system also incorporates a second transceiver 217 thatincorporates an 802.11X-based protocol(s). This transceiver is used totransmit and receive data, with an end device. The 802.11X wirelesstransmit signal is limited to maximum power by the FCC and has acorresponding range which is typically less than the range of thehost-OPP transceiver 216. The transceiver 216 typically uses a regulatedfrequency spectrum and a different power level. For example, host-OPPwireless communication may use digital cellular, WAP, or a pagingprotocols. Each of these operates on different frequencies withdifferent operational characteristics.

As the embodiment of FIG. 2 illustrates, the OPP of FIG. 3 a maycommunicate with an intelligent thermostat 2. An embodiment of theintelligent thermostat is illustrated in further detail in FIG. 3 b.Some of the components of the intelligent thermostat may be common withthe components of the OPP. In FIG. 3 b, the intelligent thermostat 270contains a microprocessor 210 that communicates with memory 214 b thatmay comprise both volatile SDRAM memory 214 a and non-volatile FLASHmemory 214 b. The microprocessor may also be connected to variouscontrol circuits, such as the wakeup timer 224, timer 222, and CPUsupervisor 220, the functions of which have already been described. Themicroprocessor 210 interfaces with a 802.11 data transceiver 217 thatuses an antenna 219 to communicate with the OPP.

The intelligent thermostat typically incorporates a display 260 thatindicates the current and desired temperatures and the thermostatincorporates a temperature sensor 264 providing ambient temperaturedata. The temperature sensor 264 could provide digital values that themicroprocessor scales to the appropriate temperature scale, or thetemperature sensor may provide an analog voltage input which isconverted to an analog to digital (A/D) converter, either incorporatedinto the microprocessor or by discrete A/D circuitry.

The microprocessor 210 controls an electronic switch 266 via a controlinterface 208. An alternative embodiment of the switch could be anelectro-mechanical switch, such as a relay. Regardless, the switch 266completes the circuit for a A/C load activation line so that the inputA/C load Activation line 268 is connected to the output A/C loadactivation line 269. When the connection is completed, the load may beactivated. In alternative embodiments, the completion of the connectionbyb the switch 266 may de-activate the load.

FIGS. 4 a-4 d illustrate embodiments of the protocol stacks that mayexist for the various configurations of FIG. 2. A protocol stack is arepresentation of the protocol layers used to implement communication ina system, and illustrates how communication occurs with other devices atvarious peer-to-peer levels. Such concepts are well known in the area ofdata communication and serve in part to model how communicationfunctions are modularized. In FIG. 4 a, two protocol stacks areillustrated—the end device protocol stack 300 and the On-PremiseProcessor protocol stack 302. In this embodiment, each system comprisesthree protocol layers, though more or less could be used and layers canbe frequently viewed as having sublayers defined.

Starting at the top layer, the Energy Management Application 306 aresides in the end device and communications with a peer application inthe OPP, also an Energy Management Application 306 b. Though theapplications are peers, this does not necessarily mean that they containidentical functionality, just that they are designed to communicate witheach other. For example, the OPP may issue a command to deactivate aload, and the end device will recognize and process the message. It doesnot necessarily follow that the end device has the capability to issuethe same request to the OPP.

The communication between the peer entities is represented by the dottedline 301 between the two protocol stacks. Although not shown, typicallysimilar peer-to-peer communication occurs between the other layers aswell. For example, the End Device Energy Management Application 306 atypically will request authorization to activate a load. The OPP EnergyManagement Application 306 b is designed to receive such a request andprovide a response. Further, the End Device Energy ManagementApplication is designed to understand the response. Such applicationsmay be defined for load management, requesting energy usage information,reporting energy related status conditions or data, and so forth. Thecommunication capability is typically defined for accomplishing aspecific application—in this embodiment, it is for energy management,but it could be used for process control systems, alarm conditions,asset tracking, etc.

The Energy Management Application layer 306 uses the services of thetransaction protocol layer, 308 a, 308 b. The transaction protocol layermay be based on the X.408/409 remote operations protocol or any othertransaction protocols, such as X.400 message handling, or IP. Otherstandard or proprietary protocols can be used. The transaction protocoltypically conveys simple transactions, comprising a ‘request’ messageand a ‘response’ message. In addition, some transaction protocols mayallow multiple intermediate messages, such as ‘continuation’ messages.The transaction protocol defines the basic message structure, meaning,and procedures for requesting data and receiving the response. It alsoincorporates procedures for indicating the presence of errors inmessages and requesting retransmission as well as acknowledging receiptof error free messages. It conveys messages defined by the EnergyManagement Application, so that the transaction protocol could conveyrequests for energy status and associated responses, or the transactionprotocol could convey requests for any other application just as easily.Typically, the transaction protocol in the end device 308 a has the samefunctionality as contained in the transaction protocol in the OPP 308 b.Thus, these are typically peers.

Finally, the transaction protocol messages are conveyed using the IEEE802.11X wireless protocol 310 a, 310 b. This could be, for example,802.11b, 802.11g, or other versions. Even non-802.11X wireless protocolscould be used, such the “Bluetooth” wireless standard. As described inthe Background section, 802.11 provides a wireless LAN like capabilityallowing the OPP to readily communicate using radio signals with the enddevice. The 802.11X protocols are peers, and communicate using radiowaves in a defined frequency spectrum that are represented as providingconnectivity 309 between the two systems.

Because each protocol layer is modular, this facilitates implementation,interoperability, and lowers cost. Thus, implementing such a system canbe accomplished by integrating 802.11X capabilities and transactionprotocol software from different vendors, focusing on the applicationlevel functionality.

In FIG. 4 b, similar protocol stacks exist for the OPP 302 and the Host304. The energy management applications in the OPP 312 a and the host312 b are not necessarily the same as in FIG. 4 a. For example, theapplications 312 may define the capability of the host requesting theOPP to poll an end device for energy related status indications. In thiscase, the host is not directly requesting status indications from theOPP, but requesting the OPP obtain the status indications from other enddevices. There is great flexibility in defining the application'scapabilities, and the variations of FIGS. 4 a-d are not intended tolimit the energy management applications.

The transaction protocol layer 314 a in the OPP and the host 314 b mayvery well be the same as in the end device, but this is not required.Frequently, the OPP to host interaction may be more sophisticated andrequire additional transaction capability functions beyond that requiredfor the OPP—end device interaction. It may be that the OPP—hosttransaction protocol layer is a superset from that implemented for enddevice-OPP communication.

The lowest level protocol layer in the OPP 316 a and the host 316 b aretypically not the same as between the end device and OPP. The lowerprotocol layer in the host could be a wireline based protocol 316 a, 316b. Examples include power line carrier systems or telephony basedprotocols. The wireline connectivity is represented by line 311.Alternatively, a wireless protocol could be used, potentially based on802.11, cellular, paging, satellite or any other type of wirelesscommunication capable of conveying data.

Again, protocol layers are used to provide modularity, so that a systemincorporating OPP-Host communication can be adapted with minimalchanges. For example, an OPP-Host communication system incorporatingpower line carrier lower protocol layers could be adapted to wirelesscommunication by replacing the lower protocol layer without having toreprogram/modify the transaction protocol layer or the applicationlayer. Other implementations may have additional layers, such as anetwork layer, for providing connections to a plurality of nodes on anetwork. For example, an OPP may desire to connect to one of severalhosts, and this would require an addressing capability that may justifyusing a network layer protocol. This could be, for example, based on theIP protocol.

Turning to FIG. 4 c, an embodiment of communication between the enddevice 300 and host 304 is depicted where the OPP protocol stacks 302 a,302 b function to relay transaction messages. The OPP protocol stacks302 a, 302 b essentially combine the stacks of FIGS. 4 a and 4 b, withthe exception of the energy management application in the OPP. As willbe discussed, other embodiments may actually incorporate the energymanagement applications in the OPP.

In the embodiment of FIG. 4 c, the energy management application in theend device 320 a communicates with its peer corresponding to the energymanagement application 320 b in the host as represented by dotted line317. This means that the two protocol layers are peers, and must bedesigned to be compatible. This architecture has advantages anddisadvantages. The advantages include that the application does not haveto be deployed by the OPP and the relative simplicity of operation inthat the OPP simply relays transaction messages from one side to theother. A disadvantage is that once the end devices are deployed, thecorresponding application must be present in the host. This means thehost application may be ‘frozen’ as long as the end devices in the fieldare supported. This significantly complicates upgrading the host sinceit is unlikely that all end devices will be upgraded at one time. Thus,the host may be required to support multiple versions of the energymanagement applications simultaneously.

In FIG. 4 c, the end device energy management application 320 a uses thetransaction protocol layer 308 a which in turns uses the 802.11X-basedwireless protocol 310 a to communicate using radio waves 309 to thecorresponding 802.11X-based wireless protocol layer 310 b in the OPP, aswell as the corresponding transaction protocol layer 308 b. The routingand relaying function 322 receives a transaction protocol request on oneside 302 a of the protocol stack, that is, a protocol request receivedfrom the end device, and maps the protocol message to the othertransaction protocol request 314 a compatible with the host transactionprotocol 314 b. The information is conveyed from the OPP using awireline protocol 316 a that is conveyed using a physical medium 311 tothe corresponding wireline protocol 316 b in the host 304. Otherembodiments could use other protocols for the lower stacks 316 a, 316 b.

FIG. 4 c indicates that the protocol used to convey information from theend-device to the OPP for the lower layers, may not be the same protocolto convey the information from the OPP to the host. Specifically, thephysical medium, protocol layers below the application level messagesmay be different and mapped as required by the OPP. Alternatively, someor all of the lower layers may be the same, and the OPP simply relaysinformation with a minimal of protocol conversion. Regardless of theparticular embodiment used, the energy management application 320 a inthe end device protocol stack 300 is able to communicate logically 317with the energy management application 320 b protocol layer in the hostprotocol stack 304. This architecture requires that the two energymanagement applications in the end device and host are compatible, andthis minimizes complexity by minimizing the mapping functions in theOPP. However, if new and advanced energy management applications aredeployed with additional messaging functionality, then the host must beupgraded as well. If all the end devices are not upgraded at the sametime, then the host must implement multiple versions of the energymanagement applications and track which version each end devicerequires. This complicates the operation of the host system as it mustmaintain and track each version.

FIG. 4 d illustrates another embodiment that alleviates theaforementioned host requirement, but it does involve additionalcomplexity in the OPP. In FIG. 4 d, protocol stack 300 for the enddevice and a protocol stack 304 for the host are present, as well ascorresponding protocol stacks 302 a, 302 b in the OPP for communicatingwith the end device and host respectively. However, in this embodiment,the energy management application messages are terminated and processedin the OPP. This is indicated by the routing and relaying functions 322in the OPP occurring above the energy management applications 312 b, 323a.

A typical end device—host interaction starts with the end device energymanagement application 321 a initiating a message that is conveyed bythe transaction protocol 308 a, which in turn is conveyed using a802.11X-based 310 a wireless protocol. This is wirelessly conveyed usingradio waves 309 to the OPP. There, the radio waves are received by the802.11X-based wireless protocol receiver protocol handler 310 b thatprovides the information to the transaction protocol layer 308 b, whichin turn, provides the message to the energy management application 321b. At this point, the energy management application processes the energymanagement message, and determines the appropriate action. In thisembodiment, the application determines the message is to be routed andrelayed to be communicated to the host. Thus, the application in the OPPis involved in determining how to process the energy managementapplication message. A corresponding energy management application 323 areceives the message from the routing and relaying function 322 andformulates a message that is passed down to the transaction protocollayer 314 a, which in turn passes it down to the wireline protocol layer316 a, which in this embodiment is a TCP/IP protocol. This is conveyedby a physical medium, such as a cable 311 and received by the hostsystem wireline protocol handler 316 b and passed up to the transactionprotocol layer 314 b, which is turn is passed up to the energymanagement application 323 b.

In this embodiment, the communication 317 from the end device energymanagement application terminates in the OPP, but the OPP is“intelligent” enough to relay the message using a potentially differentenergy management application between the OPP and host. Thecommunication between the OPP and host may involve a differentapplication protocol than between the OPP and end device. As long as theOPP can handle the different end device protocols, it is possible forthe host to implement only a single energy management application. Forexample, an OPP maybe deployed that handles two versions of an energymanagement application that are located in two different types of enddevices. The OPP can handle either type of end device, or both, andconvert messages from either end device to a single energy managementprotocol to the host processor. The OPP determines the appropriateprotocol to use when communication with the end device based on theaddress of the end device. Thus, each time a new energy managementprotocol is introduced into an end-device, the host does not necessarilyhave to be upgraded, but the OPP must be upgraded. This may occur bydownloading additional software to the OPP.

The embodiment of FIGS. 4 c and 4 d illustrate an end devicecommunicating to the host using a single OPP. As previously noted, theOPP may be embodied by a circuit board integrated into a power meter.This arrangement provides a convenient means for regulating and ormonitoring power consumption for loads attached to the output of themeter. The embodiment of FIGS. 4 c and 4 d illustrate a single OPPacting to relay information between the end device and the hostprocessor. If all information between the end device and host isfunneled through a single OPP, then determination of where informationis to be relayed to is straightforward. For example, all communicationfrom end devices received by the OPP is directly routed to a singlehost. As illustrated in FIG. 4 d, the communication between the OPP andthe host may occur using the TCP/IP protocol of the Internet. As is wellknown in the art, a sub-net on the Internet may comprise a series ofrouting hubs routing information from the originating address to thedestination address. Although a single physical connection 311 is shownin FIG. 4 d connecting the wireline protocol 316 a in the OPP to thewireline protocol handler 316 b in the host, there may be a number ofrelaying Internet nodes involved.

Those skilled in the art of data communications will appreciate othervariations are possible, and FIG. 5 illustrates other forms of networksthat could be used as a distribution network between the OPP and thehost. FIG. 5 illustrates the OPP 4 communicating with the host 6 usingone or more of distribution networks 40,42,44,46, 48. These are termed‘distribution networks’ since the networks may typically be used tofacilitate communication of a plurality of OPPs (though only one isillustrated) with a single host. This does not preclude a single OPPfrom accessing multiple hosts.

The OPP may access a distribution network that is based on a variety ofcommunication technologies. For example, a paging network 40 may be usedto communicate information between the OPP and a host. Such technologyhas been developed and uses a two-way paging capability to send ASCIIbased messages between a power meter and host processor. The paginginfrastructure is well known in the art, and provides low bandwidth datatransfer to a large number of widely distributed paging terminals. Thisdistribution network requires compliance with the appropriate FCCregulations regarding transmission of information in the specificfrequency band.

The OPP 4 alternatively can communicate to the host computer using apower line carrier network 42. This network provides communication usingthe power line infrastructure as the physical medium for transferringdata using a high frequency carrier signal. Although various limitationsmay be present due to various power components affecting the signal,this network is well known in the art as well. This network also has theadvantage that every residential and commercial location with power froma power utility has connectivity via the power distribution network.Thus, the power distribution infrastructure itself can be used to conveypower load management information.

The OPP 4 could also use the telephone network 44 to convey informationto a host, using well-known modems for data transfer. Typically, abandwidth of 56 kps is available using low cost modem technologies thatare well known in the art. Typically, locations having access to powerservice also have access to telephone service, though the power metermay not necessarily be conveniently located to the appropriate telephoneline.

The OPP 4 could also the use cable network 46 to convey information tothe host 6. The cable network is frequently available in urbanresidential locations. The OPP may access the cable network by having aphysical connection to the cable network or communicate using802.11X-based wireless protocols to a cable set top box interworkingdata to an IP service provided on cable, typically using an industrystandard cable modem standard (e.g., DOCSIS).

Finally, the OPP 4 could access the host 6 using a cellular/PCS network.These wireless networks are also fairly ubiquitous. While providingvoice service, they have been adapted to provide data transfer, e.g.,via GPRS protocols, EDGE protocols, Short Messaging Service, cellulardata modems, etc. The use of wireless cellular/PCS capabilities requiresan appropriate transceiver integrated into the OPP, and requiresappropriate FCC regulatory approval.

Each of the above schemes has relative advantages and disadvantages. Forexample, some schemes require regulatory approval or equipmentcertification (e.g., transmitting on a specified radio frequency) andrequire that the equipment be certified for use on that frequency. Otherschemes may require local wiring, for example physical connection of aphone line or cable line to the OPP. This may increase installationcosts as the access from the telephone line or cable drop may not alwaysbe nearby to the power meter. Further, not all types of distributionnetworks may be available in the desired service area (e.g., cableservice may not be available in rural or industrial areas). Finally,certain schemes may be more operationally difficult to install ormaintain.

Another embodiment of a distribution network is shown in FIG. 6. In thisembodiment, the OPP devices themselves function as relaying nodes. TheOPPs can communicate using TCP/IP high layer protocols using an802.11X-based wireless protocol, which is designed to convey TCP/IP. InFIG. 6, an end device 2 is communicating with the ultimate destination,the host 6. A grouping of intermediate OPPs function as network routingand relaying devices known as a ‘mesh network’ 20. The OPPs in the meshnetwork 20 function as network nodes in this application, not as OPPs 4a communicating with an end device. On the other hand, OPP 4 a functionsas an OPP communicating with an end device. The mesh network comprises aplurality of OPPs 4 b-4 e communicating with each other through a seriesof limited distance hops in order to reach the host.

In this particular embodiment, the end device 2 is within thetransmission range of an OPP 4 a. The transmission range is illustratedfor the OPP 4 a using a circle 5. This represents the range of the OPPfor a given transmitter power level. Thus, if end-device transmitting iswithin the range 5 of the OPP 4 a, then the end device will be able tocommunicate with the OPP, and vice versa.

The end device is illustrated as just within the range 5 of the OPP 4 a.In turn, OPP 4 a is able to communicate to OPP 4 b since they are withincommunication range of each other, which in turn is able to communicateto OPP 4 c, then to another OPP 4 d, then to another OPP 4 e, then inturn, finally to the host 6. The mesh network can be modeled in a numberof ways from a protocol layering perspective. For example, the meshnetwork 20 may function in the aggregate as the single OPP comprisingthe protocol stack 302 a, 302 b of FIG. 4 c in which applicationinformation is transparently passed between the end device and host.Alternatively, the mesh network 20 may function in the aggregate as thesingle OPP comprising the protocol stack 302 a, 302 b of FIG. 4 d wherethe application level messages are processed. Further combinations arepossible. For example, as embodied in FIG. 6, a select number of OPPs 4b-4 e may serve as a network to OPP 4 a. Thus, OPP 4 a communicatesdirectly to the host using the other OPPs as a network service provider(e.g., a subnet of the Internet).

This scheme requires less regulatory compliance compared to other formsof wireless transmission since the 802.11X-based suite of protocolsoperates in the unlicensed frequency band. However, FCC regulationsstill require transmission within certain power levels. The typicalrange of such units is flexible and depends on the power levels andtransmission bandwidth. As the number of OPPs is deployed, the averagedistance to the nearest OPP decreases and the required power levels canbe decreased.

Typically, the TCP/IP protocol is used for addressing messages betweenthe various elements. The 802.11X-based suite of protocols is based onusing TCP/IP and incorporates the well-known IP addressing scheme usingMAC (media access control) addresses. MAC addresses uniquely identify anode on a LAN, and FIG. 7 illustrates how various types of end devicescan communicate with the OPP. In FIG. 7, each of the end devices isassigned a MAC address. This can be programmed into the device atmanufacturer, or dynamically assigned. In FIG. 7, the end devicesrepresent typical control devices communicating with the OPP, includinga thermostat control 2, an alarm system 30, a water meter 32, a cableset top box 34, an appliance 36, and a gas meter 100. Each end devicecommunicates using a wireless 802.11X-based protocol to the OPP 4, whichis illustrated as co-located with the power meter. The power meter isusually affixed to the exterior of a residence or commercial building,and the end devices are typically within the range of the OPP 4 locatedat the same premise. Typically, the distance between the end device andOPP is no more than 100-200 feet. Because it is possible that there maybe several OPPs co-located into power meters within the range oftransmission of the end-device and OPP, a scheme for registering theend-device is required. This could involve remotely programming the OPPwith the appropriate 30 address for each end device, or using anauto-registration procedure where a defined time period is establishedboth in the OPP and the end-device to send/receive and register addressinformation. Alternatively, each end-device could be locally programmedto enter the address of the OPP. Such mechanisms are indicated in802.11.

FIG. 8 summarizes several of the inventive aspects of the aforementioneddiscussion in light of an energy management application. In FIG. 8, anend device 2 recognizes the presence of a nearby OPP 4 functioning as arelay of information allowing the energy management application in theend device have peer-to-peer communication 56 with the energy managementapplication in the host 6. The OPP 4 relays information using adistribution network, which is embodied as a mesh network of other OPPs20. The mesh network 20 has connectivity with the host 6 via aconnection 54. It is possible that the ‘last’ OPP in the mesh network isactually hardwired via a connection 54 to the host via a wirelinecommunication facility (e.g., T1 connection).

The energy management host computer 6 is further defined in FIG. 9. InFIG. 9, the energy management host comprises various processing relatedcomponents. The processing system 72 is typically a large-scale servercapable of processing simultaneous communication with numerous remoteend devices. An operator console 73 allows administration of the variousend-device accounts, including creating, editing, and deleting accounts,and other operational related functions. Various system statusindicators can be provided on the operator console 73 as well as theprinter 74. The printer is typically used to print out period reports.The processing system 72 also accesses memory 76 used to store variousdata and application programs. This includes: the main energy managementapplication, including a meter reading application 77 a, data pertainingto when each meter is read (typically based on the customer's billingcycle) 77 b, the report generator application which takes the meterreading data and aggregates it into the desired form 77 c, an accountmanagement application 77 d allowing new 25 accounts to be establishedor edited, and an alarm generator 77 e used to indicate an abnormalstatus. Although other applications and data may be present, theseillustrate several aspects of a typical energy management application.

The processing system 72 is also connected to a communication interface71, which in turn connects to the distribution network 54. Since avariety of distribution network technologies may be used, thecommunication interface 71 allows the remainder of the host processingsystem, namely processing system 72, to be independent of the particulardistribution network used.

The processing system 72 also accesses a database 75 for storingmeter-reading data. Typically, meter-reading data are stored on ahistorical and present basis. Historical data may be stored in aseparate database with slower performance requirements. Present data istypically accessible on a real time basis, since information of currentusage is typically compared with recent past usage in previous years.Thus, the storage and reliability requirements may be different.

A typical record format 80 stored in the database 75 is illustrated inFIG. 10. In FIG. 10, a meter identification number in the column header81 is used to identify a particular meter's data. In this embodiment,four separate meters 84 a-84 d are shown, though typically data forthousands of meters are stored. Typically, the meter numbers aredetermined by the energy service provider or meter manufacturer, and maynot necessarily identify the customer's account. The next column 82identifies the customer account's rate plan, which indicates how billsare calculated based on usage. Typically, additional rating plan data isaccessed based on the plan identifier. Next a MAC address 83 indicatesthe necessary address used to communicate with the particular meter. Itis possible that other address schemes could be used. The next column 84indicates the activation status and date for that meter. The hostrecords the status as to whether a meter is active or inactive. Forexample, a meter may be ‘shut off’ to disconnect power when a residenceis vacated. In this case, the meter would be labeled as ‘inactive’ andthe date (and possibly time) of the event could be recorded.Specifically, meter identification number 2350-529345 81 c is indicatedas inactive as of Jun. 3, 2003 (Jun. 3, 2003) 84 c. The next meteraccount 84 d is indicated active as of Jul. 11, 2001 (Jul. 11, 2001).

The host may maintain in each record a load restriction status 87. Thisfield indicates whether the customer is participating in a loadreduction program. Specifically, if ‘allowed’, the customer is willingto receive and act upon a load reduction request in exchange,potentially, for a favorable billing rate. In FIG. 10, one account hasindicated 87 d participation in load reduction. Further, the indicationis listing as ‘Allowed, Active’ 87 d indicating that load reductionprocedures are currently active for that account. The host may maintaininformation regarding typical load reduction amounts for each customer,and use that in determining an aggregate running load reduction when aload reduction initiative is pending. Thus, a host may issue loadreduction requests until a threshold of aggregate load reduction levelhave been met, at which point the host may not longer issue suchrequests. Further, the host may prioritize certain customers based onload size or other factors. Although not illustrated in FIG. 10, thehost may maintain records (e.g., another column indicating) for eachcustomer participating in the load reduction program if the customer wassent a request and subsequently rejected by the customer. In otherwords, the customer received the request to reduce their load and chosenot to reduce their load. The host may ‘flag’ such customers for notparticipating in load reduction so that any predefined economicpenalties can be calculated.

Also included for each meter are various meter-reading data. Forexample, column 85 indicates the first reading, and the next column 86indicates the next meter reading, and so on. Typically, a finite timeperiod of data is retained (e.g., the 12-24 months) in the presentdatabase. For example, the meter of row 81 d has an initial reading of34.5 units measured at 12:48 p.m. on Jun. 3, 2003 85 d. The meterreading data typically includes the current reading and the time anddate the reading occurred. Other variations on the data structure arepossible. Although the embodiment of FIG. 10 illustrates meteringreading data as usage related data, ‘meter reading data’ as used hereincan refer to any type of data collected from a meter, and is not limitedto only usage data, but can refer to status, time, and any other type ofdata measurements retained in the meter, including power qualityaspects, low voltage indications, frequency variations, etc. Thoseskilled in the art will recognize a variety of parameters that can beread, stored, and transmitted to a host.

Now that the communications architecture and host processing system havebeen discussed, various energy management applications are presented.One such application is the limiting of power consumption by major powerloads. Typically the power utility companies maintain a list of largepower consumption users. If power consumption within a region reaches athreshold, the power utility will typically telephone these customersand request that they voluntarily lower their power consumption. Thistypically occurs by the customer voluntarily turning off loads, such asair conditioning systems, for a limited time.

Power companies may offer reduced rates to customers if customersvoluntarily reduce their consumption when requested. The procedures forreducing power consumption is largely a manual process, and automatedprocedures using the aforementioned architecture would facilitate suchsituations.

In FIG. 11, a system for automating such requests for power reduction isillustrated. A host system 6 manages the power system demand. The host 6receives various real-time inputs (not shown) of current powerconsumption in various serving areas associated with the power grid. Thehost also employs an energy management application determining when aload threshold has been reached, warranting the indication of an alarmrequiring the voluntary reduction in power from various customer loads.The host typically maintains a database of all the customer energyloads, including their load characteristics, their relationship to thepower distribution grid, and associated contact related information.Typically, the host initially identifies customer loads for energymanagement. For example, power loads may represent critical applicationswhere power cannot be reduced (e.g., hospitals, emergency responders,etc.) and are not suitable for energy management.

When the circumstances require, the host 6 issues a ‘power demandstatus’ indicator 93 that is communicated to a target OPP 4. Thecommunication may occur using a variety of the distribution networksidentified, such as the aforementioned paging network, and using eitherstandard or proprietary signaling. The message is sent from the host tothe OPP and terminated at the OPP. The message 93 may include a timeduration indicating a default duration or requested time duration (e.g.,four hours) that the power restriction procedures are in place. The OPPhas a timer so that the appropriate amount of time can be determined.Alternatively or in addition, a follow up message terminating the powerrestrictions can be issued by the host. The recording of the statusindication as well as each customer's response can be incorporated intoeach embodiment, but is only illustrated in this embodiment for brevity.In this embodiment, the OPP is integrated into the power meter and isable to control the flow of power as required in various applications.The ‘power demand status’ indicates the presence of a ‘high powerdemand’ condition. This is triggered when power demand is, or isprojected to, exceed a pre-set threshold. The receipt of this message bythe OPP in this embodiment does not result in termination of power bythe power meter. Rather, the OPP simply records this status in order torespond to a request from a load controller for permission to activate aload. Similarly, the host can reset the power demand status (indicatingthe absence of a ‘high power demand’ condition) by sending a subsequentmessage altering the status indicated.

The ‘power load’ in FIG. 11 is represented by the intelligent thermostatcontrol 2. In practice, the intelligent thermostat 2 is the controllerof an air conditioning system, and the actual load is the motor runningthe compressor in the A/C unit. However, since the intelligentthermostat controller activates the A/C unit, the controller is used torepresent the power load.

Whenever the intelligent thermostat 2 determines that load activation isappropriate, it will first initiate a “request message” 90 to the OPPrequesting authorization to turn on. Since the intelligent thermostatdoes not know the power demand status, it must first check with the OPP.The OPP 4 receives the request and reads the current power demand statusindication that it previously received from the host, which is stored innon-volatile memory. The OPP processes the request 91 and responds tothe controller with a “response message” 92. The “response message” mayindicate authorization or denial to activate the load.

This energy management communication architecture supports two differentenergy management schemes. In the first scheme, the OPP has absolutecontrol over whether the intelligent thermostat can activate its load ornot. The “response message” directly controls the operation of the enddevice. In some scenarios, this type of energy management may bedesirable. However, there are numerous applications in which thecustomer would like to chose whether they would voluntarily comply withthe request to lower power consumption or not. In this secondarchitecture, the ‘response message’ indicating authorization or denialto activate a load is only an advisory indication from the OPP. Theintelligent thermostat after becoming aware of the status, thendetermines on its own whether to activate the load or not. This allowsthe customer to have final control over any voluntary reduction of loadconsumption.

The architecture presented in FIG. 11 is characterized by: informationbeing transferred between the host and the OPP, the OPP processing andstoring the information, and the OPP subsequently interacting with theend device. The architecture also presumes that the intelligentthermostat will query the OPP prior to each activation. This may resultin unnecessary requests communicated to the OPP, particularly during atime when there are no power restrictions (e.g., during the wintertime). Those skilled in the art will recognize that additional messagesmay be defined to improve the messaging efficiency. For example, manypower load problems occur in the summer months when A/C usage is at apeak. A host processor can often predict when power load restrictionsare required (e.g., comparing recent usage and forecasted temperatures).The power system host can issue a command to the OPP requesting the OPPto indicate to the end-devices that the end devices should requestauthorization before activation until notified otherwise. In thismanner, a host can predict for a given day the possibility ofrestrictions and notify the OPPs to notify the end devices that loadactivation requests should occur. This allows ‘deactivating’ the energymanagement system as needed (e.g., during winter) and ‘reactivating’ thesystem when required (e.g., during summer).

Another variation of the previous control architecture involves the enddevice querying the OPP prior to load activation, but the OPP defaultsto authorizing activation unless a power restriction indication has beenreceived from the host. If a power restriction indication was received,the OPP will initiate a query to the host indicating the particular enddevice that is requesting load activation. The host response is receivedand relayed by the OPP to the end device. In this manner, the host isnot burdened with handling load activation request until the host firstnotifies the OPP. However, the OPP is burdened with processing messagesfrom the end device. Similarly, once conditions warrant, the host canindicate the absence of a power restriction to the OPP, where after theOPP defaults to approving load requests from the end device.

FIG. 12 embodies another variation of managing power consumption in apower load. In FIG. 12, the intelligent thermostat 2 again initiates a‘request message’ 90 to the OPP. The OPP 4 recognizes the requestmessage requires determination of the power demand status, and inresponse generates a query to the host 6. The query message is a“request message” 95 requesting the current power demand status. Thehost receives the message, and based on determination of the powerdemand status, the host responds with a ‘response message’ 96 that issent to the OPP. The OPP recognizing that a pending response the enddevice is required, generates a ‘response message’ 92 with theappropriate authorization or denial.

Whereas the OPP in FIG. 11 processes requests from the end deviceautonomously, the OPP in FIG. 12 processes each request from the enddevice by relaying a corresponding message to the host. In thisarchitecture, the OPP terminates messages from the end device, andinitiates a separate message to the host. Thus, there is a “firewall” 94created by the application in the OPP between messages from the enddevice and messages to the host.

In FIG. 13, another embodiment is illustrated. In this embodiment, theOPP is largely unaware of the energy management application.Specifically, the OPP functions to relay a message received from an enddevice in one protocol by mapping it to another protocol sent to thehost. The OPP may, in some implementations, convert the messages fromthe end device from one physical protocol (e.g., 802.11X) to anotherprotocol, based on the distribution network protocol used between theOPP and the host.

In FIG. 13, the request message 90 is generated by the intelligentthermostat 2 to the OPP 4. The OPP is only required to map the messageto a predetermined address associated with the host 6. The requestmessage from the end device 90 is mapped to a request message 97 to thehost. The OPP may or may not be aware of the meaning of the messages,namely that the message is a request to activate the power load. Thehost 6 does interpret and process the message, and returns a responsemessage 98 that is received by the OPP 4, which in turn maps thecontents to a message 92 and transmits it to the end device.

FIG. 13 also allows illustration of another concept that can apply toother embodiments. Namely, after the host 6 responds with the responsemessage 98, the host may record the load restriction status (column 87of FIG. 10) in a data structure associated with the customer. Thisallows the host to maintain current indications of whether a loadrestriction request is pending for a given customer. The host mayestimate the load ‘savings’ for each account and maintain a summary ofthe total load ‘savings’ for all customers with a pending loadrestriction. Alternatively, the host may then on an interim basisfrequently read usage data from those customers to determine in realtime the load reduction that has occurred from initiating a series ofload reduction indications. In this manner, the host using the datastructure and potentially in combination with the other meter readingcapabilities, may be able to obtain feedback regarding the effects of aload reduction initiative.

In other embodiments, the host system can also provide data to the OPPthat is used by the OPP to process requests subsequently received by theOPP for yet another variation of energy management. For example, an‘intelligent’ appliance may obtain power rate information prior toactivating itself. Such rate information could include times when‘off-peak’ and ‘peak’ billing rates occur. Specifically, an appliance orpower load may initiate a query for information regarding current powerrates and use such information in determining whether to activate thepower load. Many appliances, such as A/C units, refrigerators, anddishwashers may be able to defer activation for a short time period ifpower rates are reduced in the near future. This is embodied in FIG. 14.In FIG. 14, a power system management host 6 sends a notificationmessage 120 conveying power rate data. This data typically includes atime schedule indicating the absolute or relative rate data for powerconsumption. For example, ‘off peak’ power rates could be indicated asoccurring from 10:00 p.m. to 6:00 a.m. The host 6 periodically providesthis information to the OPP 4 that stores the rate data in its memory.This could be done on a daily basis reflecting anticipated power demand.

Subsequently, the intelligent appliance 126 illustrated here as adishwasher, initiates a query 122 requesting information regarding therate status. As with the other embodiments, the communication typicallyoccurs using one of the 802.11X-based suite of wireless protocols. TheOPP 4 receiving the message performs internal processing 121 to retrievethe rate information stored. The OPP 4 then generates a response message124 containing the rate data. The OPP may provide a subset of the ratedata in the response, e.g. only that data of the schedule pertaining tofuture times. Upon receipt of the rate data, the intelligent appliance126 processes the rate data 125 to determine whether it should selfactivate or defer self activation until an ‘off-peak’ rate occurs. Inthis manner, information from the power system management host 6 can bedisseminated to a plurality of OPPs, which in turn disseminates theinformation to an end device allowing the end device to determinewhether it should activate or defer activation of a power load.

Another variation of the end device obtaining rate information ispossible in which the end device sends a query for rate information tothe OPP, and the OPP relays the request to the host. The host respondsto the OPP and in turn, the OPP relays the response to the end device.This message flow would be analogous to the message flow of FIG. 12where the OPP functions to rely information between the end device andhost.

The aforementioned system is not limited to energy management for loadactivation, but can also be used to read data from an electrical meter,or other types of meters. One such embodiment is illustrated in FIG. 15involving reading values from a gas utility meter. In FIG. 15, the host6 is a meter reading management system that issues a command 110 to theOPP 4 directing the OPP to read information from the indicated meter.Typically, the meter is identified by a particular address, such as theaforementioned MAC addresses. The OPP 4 receives the request anddetermines via an address table in memory if there is an establishedassociation with the indicated address. In the embodiment of FIG. 14,the OPP 4 is in the nearby vicinity of the three utility meters asindicated by the dotted line 101—the power meter (integrated with theOPP 4), the gas meter 100, and the water meter 32. Thus, the OPP 4 mayhave established a table with addresses for each of the meters and knowsit is able to communicate with each meter. In the case of the gas meter100 and water meter 32, the OPP typically communicates using one of the802.11X-based suite of protocols. In the case of the electric meter,reading data may be accomplished using proprietary messaging protocolsince the OPP is integrated with the power meter. Alternatively, the OPPand power meter may not be integrated and the OPP uses 802.11X-basedprotocols to communicate with the power meter. Assuming that the targetmeter is the gas meter 100 as embodied in FIG. 15, the OPP 4 issues aquery or command 112 to the target meter to read the current value. Thegas meter 100 returns a response message containing the meter readingdata 114, which is received and processed by the OPP 4. The OPP 4conveys the information in a message 116 to the host. The host thenrecords the data as required in the data structure containing the meterreading data.

Other variations are possible. For example, in FIG. 15 the OPP couldautonomously read the meter on a periodic basis (e.g., daily), and storethe data in memory. The OPP upon receiving a command from the host couldthen transmit the plurality of data values to the host. As with thepreviously illustrated architectures, the OPP may terminate the messagefrom the host and generate different application level messages to theend device (e.g., the gas meter). Alternatively, the OPP may simplyrelay the message to the end device, as well as relay the response tothe host. Alternatively, the OPP may periodically collect data from theremote meter and autonomously send it to the host, or send the data uponrequest to the host. The data measured, stored, and transmitted may beusage related data from the meter, but may comprise any other dataretained in the meter, including status, time, and various power qualityparameters, such as voltage dips/spikes, average/peak/low voltagefrequencies, maximum current draw, et cetera. The embodimentsillustrated and the phrase ‘meter reading’ is not limited toapplications only involving usage data.

FIG. 16 indicates another energy management application directed toemergency load control management. In various applications, the hostprocessor may require deactivation of a load, either in emergency ornon-emergency circumstances. In this case, the host may have absolutecontrol over the activation/deactivation of the power load. In FIG. 16,the host 6 issues a message 130 of an impending load deactivation to theOPP 4. This notification message is intended to ‘warn’ the OPP that animpending power deactivation command should be expected. The OPP 4responds with an acknowledgement message 132 indicating whether it isable to comply with a future load deactivation or not. Thisacknowledgement serves at least two functions. First, it confirmsreceipt of the notification to the host. Second, the host is able toobtain an indication of whether the load can be deactivated. Forexample, the power management host system may not maintain informationabout all the load applications under the control of the OPP.Alternatively, various life sustaining medical equipment may beoperating as a load from the power meter and the acknowledgement of theOPP may indicate that it cannot comply with a load deactivation request.This may be used by the host to avoid sending a load deactivationrequest to the OPP.

Assuming the OPP 4 acknowledgement message indicates compliance isexpected, at some time the host may issue a load deactivationnotification 134 requesting immediate shut down of all loads. Afterinteracting with the power meter to effect the termination of any powerat the output of the meter, the OPP issues an acknowledgement message135 indicating that the power load has been terminated. The host thenrecords this information and may sequence through other OPPs to reduceadditional loads until the necessary overload to the power grid isreduced.

The above sequence can be adapted to accomplish deactivation of a meter,typically for non-payment or normal termination of service. A similar‘activation’ sequence could be used to activate a meter forestablishment of service. This would facilitate normalactivation/termination of power service and avoid a service call to thelocation.

In each of the energy management schemes, variations are possible thatare included within the principles of the present invention. Forexample, although embodiments incorporating an intelligent thermostatare disclosed, the system could apply to any type of electricalcontroller, including solenoids, mechanical switches, or solid staterelays or other electronic components. The power load activated is notlimited to motors in A/C units, but any type of motor in a device,including a pump, compressor, machine, drive unit, material handlingsystem, etc. The controller is not limited to controlling power loads,but may control the flow of liquids, gases, or solids through valves,manifolds, gates, or various types of material handling devices. Thecontroller can control industrial machines, processes, lighting,sensors, detectors, or other type of devices. The control mechanism cancontrol access to locations, authorization activation of securitysystems, or activation of an industrial process. The system can be usedto activate/deactivate a device, such that the unit could be taken‘off-line’ if necessary. The unit can be remote activated once serviceis restored.

Although the embodiment discloses a residential type power meter, theOPP could be standalone or integrated into valves, machines, or any ofthe various types of controllers. The system may be used to read orwrite data from a particular device, such as reading meter data,including obtaining readings from water or gas utility meters. Theinformation obtained may be usage data, status indications, or periodicusage or rate of use information. Information other than usage that maybe obtained by a meter or device can be reported or read to/by the hostcomputer, including water line or gas line pressure readings, linevoltage, line voltage dips, voltage frequency, or any other measurableparameter.

1-42. (canceled)
 43. A method to read energy related data in a powermeter comprising: sending a request message to an on-premise processordirecting the on-premise processor to read energy related data from apower meter identified by a meter identification number using an802.11X-based wireless protocol; retrieving energy related data storedin a memory of the power meter by the on-premise processor using the802.11X-based wireless protocol and the meter identification number;receiving a response message sent at a host processor communicated fromthe on-premise processor using the 802.11X wireless protocol indicatingthe energy related data and the meter identification number; andrecording the energy related data associated with the meteridentification number in a data structure in memory of the hostprocessor along with a date and time information.
 44. The method ofclaim 43 wherein the request message to an on-premise processordirecting the on-premise processor to read energy related data from apower meter is sent from the host on a periodic basis.
 45. The method ofclaim 43 wherein the energy related data is usage related.
 46. A methodfor reading data from a utility meter, comprising: storing a utilitymeter address and a utility meter reading schedule in an on-premiseprocessor indicating a time to read data from at least one utilitymeter; communicating a meter reading request message incorporating theutility meter address from the on-premise processor to the utility meterusing an 802.1 1X wireless protocol at a time indicated by the meterreading schedule; receiving a meter reading response message at theon-premise processor containing usage related data communicated usingthe 802.1 1X wireless protocol; and sending a meter reading reportmessage from the on-premise processor to a host processor, the meterreading report message including usage data, meter type, and the utilitymeter address.
 47. The method of claim 46 wherein the utility metercomprises one from the group of water meter, gas meter, and power meter.48. A method for a host processor to read measurement data from autility meter, comprising the steps of: receiving a first requestmessage at the on-premise processor sent from the host processorrequesting measurement data from an utility meter wherein the requestincludes a meter identifier associated with the utility meter; sending afirst acknowledgment message in response to the first request by theon-premise processor to the host processor indicating error free receiptof the first request; sending a second request message from theon-premise processor to the utility meter communicated using a 802.11Xwireless protocol requesting measurement data from the utility meter;receiving a first response message at the on-premise processor from theutility meter communicated using the 802.11X wireless protocol includingthe measurement data and a date; sending a second acknowledgementmessage from the on-premise processor to the host processor includingthe measurement data and the date; and recording the measurement dataand the date in a data structure associated with the meter identifier inthe host processor.
 49. The method of claim 48 further comprising:erasing the measurement data from a memory in the on-premise processor.50. A method for a host processor to obtain measurement data from autility meter, comprising: receiving periodic measurement data at theon-premise processor from the utility meter communicated using an802.11X wireless protocol containing a utility meter identificationnumber; storing the measurement data and the identification number in amemory in an on-premise processor along with time-related data;receiving a first request message at the on-premise processor from thehost processor requesting the measurement data for the utility meter,the first request message including the utility meter identificationnumber; retrieving the measurement data and the time-related data in thememory of the on-premise processor associated with the utility meteridentification number; and sending a reporting message from theon-premise processor to the host processor incorporating the measurementdata, the utility meter identification number, and the time-relateddata.
 51. The method of claim 50 further comprising: receiving anacknowledgment message from the host processor at the on-premiseprocessor indicating receipt of the reporting message; and erasing themeasurement data and time-related data from the memory in the on-premiseprocessor. 52-70. (canceled)